@russ said in Interface possibilities:

FYI, the agent does backup your commands.json file to commands.json.backup every time you change it, and it auto-restores the backup if you make a mistake in json formatting.

Awesome, I did see the commands.json.backup file but didn't realize it auto restored.

I don't like to use the cloud for backups, however I do for some things as well as a back up on disks.

@russ Perfect! Thanks.

@tuicemen,

This is actually wrong ^. "deviceType":"light" is not a thing.

If adding that made it work, it's because when you change a command, TRIGGERcmd deletes and re-creates the Alexa smart home device. That needed to happen for the Alexa device associated with your command to have the new brightness feature.

Sorry I didn't tell you that sooner. Any newly created commands will have the new brightness and color features. Old commands just need to be changed so they get re-created. Or you can delete and re-discover them at https://alexa.amazon.com.

Also btw, only Alexa supports brightness and color so far. I'll look into Google Assistant soon.

EDIT 3/21/22: The "TRIGGERcmd Smart Home" action on Google Assistant supports color and brightness now too.

Got a lot of issues with node + brew, this one worked like a charm for me:

osascript -e 'tell application "Finder" to sleep'

@Russ Awesome. Thanks and loving the system. It solves so many issues for us.

@mikey186, thanks. I'll fix that.

EDIT: Fixed.

@Russ well never mind, I manage to find a workaround. But I would hope to see a advantage to move the PARAMs and/or more PARAMs in the future. It would be interesting.....

@CheddarLifeForm, yes that's a reasonable ask. I like the idea of a list to pick from better than using the voice names. I'll work on it.

@LR2, I added this feature just now.

Now you'll get an email if you try to run a command on an agent that's not connected.

@Kingnabis, please explain. What would you want to accomplish? Do you want to be able to send a parameter when you tap widget icon?

@glauco-keniti-inoue, currently it's not possible, but now that you've asked, it's on my todo list.

@Russ Thanks for the clarification. That was my understanding as well - to share TRIGGERcmd for all, either everybody has to use Voice Match or nobody can use it. Unfortunately, the children really want to use the Voice Match (required to teach Google Home important things such as names of our cats etc) while both me and my wife are strictly against Voice Match for us. That means that the children could share TriggerCMD but no solution for the adults. And we'd need TriggerCNS exactly mainly for the adults...

I understand it's a relatively specific situation though, so probably no solution will be available. I was hoping for something similar to Spotify (that works also for non-VoiceMatch members of the household) but I understand it may be difficult to achieve. Thanks for your efforts anyway!